Add OpenRISC 1000 (or1k) support #864
Conversation
|
A proposed architecture port for OpenRISC 1000 (or1k) is being discussed in this Pull Request: zephyrproject-rtos/zephyr#83933 This PR adds the requisite tools to the tool-chain. |
|
Yup, picolibc has upstream or1k support in 1.8.9 |
|
v2 of the patch-set removes the line-break added to |
|
Just rebased on |
There was a problem hiding this comment.
I have created topic-or1k branch for testing since the CI workflow changes do not apply in PRs.
Here is the result of a CI run:
https://github.com/zephyrproject-rtos/sdk-ng/actions/runs/18764695298/job/53537210188
There is an issue building GCC:
[ALL ] Error calling /__w/_temp/workspace/build/.build/or1k-zephyr-elf/src/gcc/gcc/genmultilib: No dirname for option: msoft-mul
[ERROR] make[1]: *** [Makefile:2359: s-mlib] Error 1
[ERROR] make[1]: *** Waiting for unfinished jobs....
See log_toolchain_gnu_linux-x86_64_or1k-zephyr-elf at the bottom of the run summary page for the full log.
|
I have changed the base branch of this PR from |
Signed-off-by: Joel Holdsworth <jholdsworth@nvidia.com>
@stephanosio Thanks. This will be very helpful. To fix the issue, I have been running the build locally in the crosstool-ng Ubuntu 22.04 docker image. The solution is to disable Because OpenRISC has no need to support multiple floating-point or ABI variants at present (no FPU/hard-float vs. soft-float distinction), a demultilib build is the only valid configuration. The or1k GCC configuration assumes a single ABI and option set; using multilib is redundant and unsupported. |
4 participants
No description provided.